Repository navigation
fix: harden report publication and serialization - #19
Conversation
CompleteDotTech
left a comment
There was a problem hiding this comment.
Independent peer review by gpt-6.1-sol at max reasoning, pinned to f8e5ddf4ab6b4a119cf5f10405e7950d502ef606. No actionable findings in this focused publication/serialization delta.
Read repository instructions, required docs, actual base/head diffs and PR discussion; verified a clean exact local pin, source SHA-256 and release checksums where present. Full offline suites pass on Python 3.10.20 and 3.14 (61 tests each). Advisory constants and assessment/input ASTs are unchanged.
13 additional reviewer-owned cases pass on each interpreter: applicable JSON/CSV/HTML publication interrupts, completed-byte preservation, pre-publication recovery, guarded success assignment, competing inode/symlink distinction, single-write interrupted stdout, actual CLI CSV NUL rejection/no-clobber, and controlled NetScaler usage errors. No target traffic, exploit payloads or real inventory data were used. This delta review preserves the existing advisory limitations and exploitability=not_tested.
Hosted checks are completed/success at the same exact head (8/8). hosted run 1 hosted run 2
COMMENT records an independent peer review; it does not claim a GitHub approval from a separate account. Merge must retain the expected-head SHA guard and normal repository gates.
Report serialization is buffered before stdout publication. CSV U+0000 fails consistently with operational exit2 and preserved files; publication interruption returns130 without a second output document.
Validation: 61 local tests pass on Python3.10.20 and3.14, with actual CLI/syscall/flag-line/competing-inode counterexamples and pre-fix failures; advisory/schema constants and assessment/input function ASTs are unchanged; checksums and whitespace checks pass. Independent Sol6.1-max review and exact-head hosted CI are required before merge.
Closes #18